each row states the floor it claims, and the page is conditional where it must be - #63

Two commits, two concerns: the floor deliverable from the timing-record card, retargeted, and the one paragraph the publication flip missed.

The floor

pacedFloor lived inside pacingFor's body, so four rows asserted a minimum none of them had written down — a global claim every caller inherited without saying so. It is now a parameter with no default, so a caller cannot inherit one by omission: omitting it does not compile.

Each caller derives its own from its own entry's record — eight times that leg's recorded block point, the multiple the retired constant was reverse-engineered from, applied per leg instead of approximated once for all three.

The numbers move, and two legs move down

Both entries, identical figures. Those two legs were floored at 6 MiB by inheritance, which is the defect — but the consequence is that their paced phases shrink, and only CI can say whether their assertions still hold. Darwin's own recorded mutation puts its margin at 300 ms, so this is not a free change. Flagging it rather than letting a green darwin gate imply three green legs.

The row rejected my first shape, and was right to

Each site originally derived the floor and then assigned the shared value inside an if !Measured() fallback. Every leg is measured on both entries, so that branch was dead code — and a dead else naming a shared constant is an inherited claim wearing a conditional. The row reddened all four sites.

The honest shape refuses an empty record instead: there is nothing for these rows to size a fixture from, and substituting a minimum would be invisible at the call. So unmeasuredLegFloor is now referenced by no call site — it stays documented as the value a caller passes deliberately, having reasoned about an empty record, not as a default anything falls back to.

The row reads source, not values

A caller whose leg has a measured record must not name the shared identifier. The number cannot answer that: eight times a block point can land on a shared constant by arithmetic accident, and two reasons producing one number is the confusion this change is against. It reds on scanning nothing, derives its file list rather than hard-coding it, resolves the one single-assignment alias this package uses, and fails on an alias it cannot resolve rather than passing over a caller it cannot see.

Mutation: control green; the shared floor restored at one measured site reds this row alone, naming file, line, row, entry, leg and block point; revert byte-identical to sha256 457242f3…; green after it.

The page

## What this is still said curious "packs an Astro project, sends it to curious.pub, and hands you back a public address" — flat present tense, three lines above a Try-it section written in the conditional. It now reads "once the platform is up", with its reason in its own sentences. A page true above the fold and false one heading down has still told its reader something untrue.

Gate

make ci exit 0, zero --- FAIL, all five affected rows passing on both the race and plain legs, three declared skips and no undeclared one. surfacecheck over 3a31014..509fdd4: 2 published surfaces, clean.

Divergence from the ruling's letter, stated

The ruling said the empty-record default "stays as the only shared value, stated at the site". It stays, and no site states it — because the row forbids naming it on a measured leg and every leg is measured. If you want the weaker row that tolerates a guarded fallback, say so and I will change it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XfBYBGuUkF7zUnZfAFD3dW